Rate limiter #894
Closed
Rate limiter #894
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
YarekTyshchenko
force-pushed
the
RateLimiter
branch
from
c916be5
to
231a466
Compare
YarekTyshchenko
force-pushed
the
RateLimiter
branch
from
96d8b6f
to
e566ea9
Compare
|
Any progress on accepting & merging this PR? |
|
I'm planning on reviving the other original PR imminently, but with some additional changes on top based on some minor tweaks we made in a private fork we've been running in production for the last 18 months. |
|
Thank you for trying to resurrect #666 via this PR @YarekTyshchenko. As this has been in draft for a while now I'm going to close this. I've created a new PR with the aim to get the rate limiting policy merged here - #903. Please address any comments on the functionality there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue or feature being addressed
This PR is a resurrection of #666 only because the author seems to be unreachable. Most of the work has already been done by @reisenberger
Solves Issue #260
Details on the issue fix or feature implementation
Confirm the following